home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
034a
/
dlock10.zip
/
DORLOCK.DOC
next >
Wrap
Text File
|
1991-12-13
|
8KB
|
208 lines
DorLock v1.0
Copyright 1991 Ernie Johnson
All Rights Reserved
About DorLock
----------------------------------------------------------------------
DorLock is for bulletin board (BBS) sysops looking for a way to keep
single node doors from causing unpredictable results when used on
multi node systems - what DorLock does is locks a door when its in
use on one node, and if a second node tries to access it, a message
is given stating that the door is in use on another node, or has
been locked for maintenance purposes.
Shareware?
----------------------------------------------------------------------
I'm sure most sysops know what Shareware software is all about, and
DorLock is a Shareware program. You are encouraged to register
DorLock with the author if you plan on using it for your BBS system.
Here's how to register:
Send a letter/postcard stating your BBS name and BBS phone number
and a brief message stating you use DorLock to:
Ernie Johnson
EPIC Information Systems
P.O. Box 607
Wingham, ON
N0G 2W0 - Canada
OR,
Phone our support BBS:
EPIC Information Systems: (519) 357-1943 1200-2400 baud
(519) 357-2952 1200-38400 baud USR HST
Dual Standard
Simply leave a message to the sysop stating you use DorLock, and
give us your BBS name and phone number so we can upload other things
to your system.
Of course, any comments or suggestions you may have are also welcome!
Please note that there is no $$ charged for DorLock! Its what is
commonly referred to as $0.00 Shareware - all I want to know is if
people are using my program, and if its worth while spending the
time writing these freebie doors and documentation! Of course, I
wouldn't reject any financial donations, but if most sysops are like
myself, they need the money for phone bills, registering other doors
and hardware maintenance.
Setting Up DorLock
----------------------------------------------------------------------
DorLock will technically work on any BBS system, although the
procedure for using doors vary from system to system, I'm sure most
people will find a way to make it work on any system.
I run PCBoard 14.5a, so I will describe how it is used on PCBoard.
First, its easier to do than to say how to do it, so here is a
sample batch file for a door called "MAILDOR":
Line # Command
1 @echo off
2 j:
3 cd\maildor
4 J:\pcb\dorlock c:\pcb\pcboard.sys
5 if errorlevel == 1 goto inuse
6 maildor c:\pcb\pcboard.sys
7 del dorlock.dat
8 :inuse
9 c:
10 cd\pcb
11 board
Description:
Line 1: just turn off echo to make things look nice
Line 2: go to my file server (drive J)
Line 3: change to the Maildor directory
Line 4: run the DorLock program - its on my J: drive in the
\PCB\ directory - DorLock requires the drive, path and
filename of PCBOARD.SYS, DOOR.SYS, or others (see below)
Line 5: if the door is already locked, DorLock returns an
errorlevel of 1, so we find out if the errorlevel is 1
and if it is, go to line 8 (the :inuse line)
Line 6: the door mustn't have been locked so run the MAILDOR door
Line 7: Delete the DORLOCK.DAT file which tells DorLock the door
is locked - this line is important - or your door will
be locked until you manually delete DORLOCK.DAT
Line 8: the "label" that the if errorlevel line needs
Line 9: go back to the local drive that has the main BBS files
Line 10: go back to the PCB directory
Line 11: reload PCBoard
For most experience sysops, that should be all that is required to
get you going.
A few things to be aware of:
1) DorLock creates the DORLOCK.DAT file in the CURRENT directory -
meaning that you need to be in the door directory that you wish to
lock, or check the lock status of! You can run DorLock from
anywhere (as in example), just make sure the current directory is
your door directory.
2) Be VERY sure you delete DORLOCK.DAT after the door is run BUT
before the :INUSE label/line!
Maintenance?
----------------------------------------------------------------------
If your system is prone to crashes, you may want to add some lines to
your events that go through your door directories that are being
locked by DorLock to delete the DORLOCK.DAT file if it exists.
This will prevent your doors from being locked "for good" (or until you
manually go through and delete DORLOCK.DAT files).
Of course, if your system is very reliable, and you don't see any
problems, don't worry about it - most people won't have a need for
this part anyway.
Non-Standard Ports and Interrupts
----------------------------------------------------------------------
If you are running on different port addresses and interrupts, you
can pass a second command line option:
DORLOCK <path&name of PCBoard.sys> <PORT:AAAA:B>
where AAAA is the base address, and B is the interrupt (IRQ).
example:
DORLOCK C:\PCB\PCBOARD.SYS PORT:03F8:4
Other BBS types:
----------------------------------------------------------------------
If you are trying to use DorLock with a BBS other than PCBoard,
you will need to tell DorLock what user file you are using. You are
also on your own when setting up the door as I only have experience
with PCBoard version 14.5 and 14.5a.
Here are some samples (untested) as to starting DorLock:
DORLOCK C:\PCB\PCBOARD.SYS ;PCBoard & compatible PCBOARD.SYS files
;this one has been tested on my BBS
DORLOCK C:\PCB\DOOR.SYS ;Systems that generate a DOOR.SYS
DORLOCK C:\PCB\DORINFOx.DEF ;Systems that generate a DORINFOx.DEF
Warranty & Guarantee's:
----------------------------------------------------------------------
DorLock is in no way warranted to be free of defects, bugs, etc. It
has, however, gone through extensive testing on my BBS, and I have
not seen any adverse effects. I am not responsible for any adverse
effects it has on your system (just in case). You should take any
steps to avoid virus infection and scan the file for viruses before
using it on your system.
DorLock is copyrighted software. Please do not make any modifications
to it! I am letting you use this software for almost nothing, and
would expect some common courtesy in return. If you have suggestions
for modifications/improvements, please forward them to me through
one of the methods below:
-- Postal Mail --
Ernie Johnson
EPIC Information Systems
P.O. Box 607
Wingham, ON
N0G 2W0 - Canada
-- Support BBS --
EPIC Information Systems: (519) 357-1943 1200-2400 baud
(519) 357-2952 1200-38400 baud USR HST
Dual Standard
-- Voice --
(519) 357-1941 Eastern Time - call between 7pm and 10pm to normally
talk to the author himself (or you'll get an answering machine).
Lastly:
----------------------------------------------------------------------
Please register! Its only the cost of a postcard/stamp, or phone
call, but it would tell me if I should continue to write these
little freebee doors for fellow PCBoard SysOps and spend time writing
documentation like this. Your registration does mean a lot ot me,
and my continuation of quality software at affordable prices!